TelORB Set Up Files for AD11.4.1 and AD12

Last updated: January 15, 2001

Note! Let the loading of this page come to a complete stop, to make the internal links work.

The file examples in this document are valid for AD11.4.1 and AD12.

This page contains examples of most of the files that are necessary for running a TelORB system and its belonging IO processors. The files in this example collection are fetched from TelORB system to3 (7 TelORB processors) and the same IP addresses as specified in the TelORB Guidelines page are valid.

The following TelORB and IO set up files are currently available:

General

General file information

TelORB system building files

Envsettings
name.epct
telorb.epct
telorbData.epct
processor.epct
netred.epct
demo.epct
java.epct
omed.epct
axmp.epct
servicePlatform.epct
pools.epct

JAMBALA system building files
created at LMC (valid for AD9)

Jambala.epct
JambalaData.epct
Processor.epct

Console logs

README.txt (Start log windows and log files)
START (Start log windows and log files)
.telnetrc

IO processor files

dhcpd.pxe.conf on IO1 (Without terminal server)
dhcpd.pxe.conf on IO2 (Without terminal server)
dhcptab on IO1 (Without terminal server)
dhcptab on IO2 (Without terminal server)
dhcptab.ts on IO1 (With terminal server)
dhcptab.ts on IO2 (With terminal server)
134_138_70_0 on IO1
134_138_70_0 on IO2
134_138_74_0 on IO1
134_138_74_0 on IO2
134_138_184_0 on IO1 (With terminal server)
134_138_184_0 on IO2 (With terminal server)
hosts on IO1
hosts on IO2
hostname.exp0 on IO1
hostname.exp0 on IO2
hostname.exp1 on IO1
hostname.exp1 on IO2
hostname.hme0 on IO1
hostname.hme0 on IO2
hostname.hme1 on IO1
hostname.hme1 on IO2
start_services on IO1
start_serviceson IO2
ep_tftpd.conf on IO1
ep_tftpd.conf on IO2

General File Information Back to Contents

Regarding the epct files, either include everything in one epct file or split
it up into several epct files for a better overview. The latter is used in these
guidelines.

o File for setting up the build environment with information about e.g. which AD
  or test bed to build from, as well as information about which epct files to be
  included when building the system:
  - Envsettings

o File that includes what name the TelORB system will get after the initial
  load. The TelORB system name is changed at a software upgrade.
  Also, the file contains information about the zone identity if the TelORB
  system is part of a network redundant system:
  - name.epct                 (NAME, ZONE)

o Files that include TelORB processor MAC addresses:
  - processor.epct            (ADDRESS)
  Either
    - dhcpd.pxe.conf          (Only for Pentium III)
  or
    - 134_138_xx_0            (Only for Pentium I)
    - 134_138_yy_0            (Only for Pentium I)
    - 134_138_184_0           (Only for Pentium I) (Only if a terminal server is
                               being used)

  - networkAddresses          (IO1: /opt/telorb/axe/loadingGroup01_1/)
                              (IO2: /opt/telorb/axe/loadingGroup01_2/)
                              (Automatically created at initial load)

o Files that include IP addresses:
  - telorbData.epct           (DorbIIOPHostName, DUMP_HOST_ID, ETHSW_ADDRESSES)
  Either
    - dhcpd.pxe.conf          (Only for Pentium III)
  or
    - 134_138_xx_0            (Only for Pentium I)
    - 134_138_yy_0            (Only for Pentium I)
    - dhcptab                 (Only for Pentium I)
    - 134_138_184_0           (Only for Pentium I) (Only if a terminal server is
                               being used)

  - hosts
  - ep_tftpd.conf

o Files that include processor allocations to pools (dependent on the number of
  TelORB processors):
  - processor.epct            (PROCESSOR)
  - netred.epct               (PROCESSOR)
  - demo.epct                 (PROCESSOR)
  - java.epct                 (PROCESSOR)
  - omed.epct                 (PROCESSOR)
  - pools.epct                (PROCESSOR)

o Files that are dependent on the number of TelORB processors (also see previous
  item, i.e. processor allocations to pools):
  Either
    - dhcpd.pxe.conf          (Only for Pentium III)
                              (It is OK to include more processors than what
                               physically exist in the TelORB system. This is
                               however not valid for the processor.epct file)
  or
    - 134_138_xx_0            (Only for Pentium I)
    - 134_138_yy_0            (Only for Pentium I)
                              (In the files 134_138_xx_0 and 134_138_yy_0, it is
                               OK to include more processors than what
                               physically exist in the TelORB system. This is
                               however not valid for the processor.epct file)

  - start_services            (/opt/telorb/tools/bin/STSsw 7 7001 -log &)
                              (/opt/telorb/tools/bin/DicosSyslogClient -L -m io1
                               134.138.xx.101-107 > /opt/telorb/syslog &)
  - README.txt                (For starting consolelogs, located at e.g.
                               /home/telorb/toX/consolelogs on e.g. a local WS)

o File that includes settings depending on the number of cabinets in the system:
  - telorbData.epct           (ETHSW_ADDRESSES)

o Files that include information about which software IDPs/IDGs that are being
  used:
  - telorb.epct               (SOFTWARE)
  - netred.epct               (SOFTWARE)
  - demo.epct                 (SOFTWARE)
  - java.epct                 (SOFTWARE)
  - omed.epct                 (SOFTWARE)
  - axmp.epct                 (SOFTWARE)
  - servicePlatform.epct      (SOFTWARE)

o Files that include initial data settings:
  - telorbData.epct           (INITIAL DATA)
  - servicePlatform.epct      (INITIAL DATA)

o File that includes information about where to put backups and where to reload
  from:
  - ep_tftpd.conf

File Envsettings, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

# For ADs
set Owndir=`pwd`
cd /ipims_dicos/ipims_dicos10/dists/TelORB-AD12/
source setup.csh
cd $Owndir

# For test beds
# source /ipims_dicos/BS2/tbAD12/IP_CONF_INFO/EnvSettings.linux

# For ADs and test beds
setenv EP_WORKSPACE `pwd`/epws
setenv DICOS_FILESYSTEM_ROOT `pwd`/axe

# Build with TelORB_Base + NetRed + DemoApp + JavaApp + AXmp
alias build 'epct -t i486 -vFc -f loadingGroup01_1 -f loadingGroup01_2 -d ../axe name.epct telorb.epct telorbData.epct processor.epct netred.epct demo.epct java.epct axmp.epct'

# Build with TelORB_Base + NetRed + DemoApp + JavaApp + OmedApp + AXmp + HLR + AC + SCP
alias build_jambala 'epct -t i486 -vFc -f loadingGroup01_1 -f loadingGroup01_2 -d ../axe name.epct telorb.epct telorbData.epct processor.epct netred.epct demo.epct java.epct omed.epct axmp.epct servicePlatform.epct pools.epct'

# Print epconfig settings
epconfig l -v

Note:
If a release is to be fetched from an AD (distribution):
# For ADs
set Owndir=`pwd`
cd /ipims_dicos/ipims_dicos10/dists/TelORB-AD12/
source setup.csh
cd $Owndir
# For test beds
#source /ipims_dicos/BS2/tbAD12/IP_CONF_INFO/EnvSettings.linux
:
If a release is to be fetched from a test bed (TB):
# For ADs
#set Owndir=`pwd`
#cd /ipims_dicos/ipims_dicos10/dists/TelORB-AD12/
#source setup.csh
#cd $Owndir

# For test beds
source /ipims_dicos/BS2/tbAD12/IP_CONF_INFO/EnvSettings.linux
:

File name.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

NAME to3_ad12_initial_zone1;
ZONE 1;

Note:
The ZONE parameter is used for network redundant TelORB systems to find out which network the zone belongs to. "ZONE 1" is default, if not typed. The redundant zone should be named "ZONE 2".

File telorb.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

SOFTWARE	 
	IDP/MD14,	// Dicos_IDP
	IDP/DUO2,	// Net_IDP, To show load on processors
	IDP/MD16,	// Ethernet_IDP
	IDP/MD18,	// Java_IDP, Optional
	IDP/D3,		// KnuerrRms_IDP, Optional
	IDP/MD1;	// DbConsistency_IDP, Test IDP for MdpSynchCheck, Optional

ALLOCATE MdpSynchCheckProcessDUT TO DicosCommonPool;	// MdpSynchCheck, Optional

File telorbData.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

INITIAL DATA

# To be able to load the JavaVM that was introduced in AD11,
# the following buffer sizes have to be increased. / Michel 991202
BOOT_buffer_size = 15000000
LMR_buffer_size = 8000000
LMD_buffer_size = 8000000

#Ddbom_dbcmaTrace = 236   # DbCma
#Ddbom_dbcmTrace = 237   # DbCm

#Ddb_majorTrace =  (236, 237)

DorbIIOPHostName = "134.138.70.101:134.138.74.102"
DorbIIOPPort = 30330
#IIOP_GatewayVerbose = 0

# If set to 1, all IORinformation will be printed, default is 0
IOR_PRINT = 0

DdbLazyPurgeInterval = 60000

#DdbSynchNumberOfWorkProcesses = 10  # No of processos for DbSynch (def=10)

#CommLinkUserId = 16360

#TestMode = 1

# Level where messages to not connected ports do not get through
IpcOverloadRejectLevels = (1000, 2000, 100000)
# Level where overload warning is sent for connected ports
IpcOverloadWarningLevels = (1000, 2000, 100000)
# Level where messages are aborted for connected ports
IpcOverloadAbortLevels = (2000, 4000, 100000)

StopInMonitor = 0
#StopInMonitor = 1

#IpcDebugLevel = 0
#IpcPortTableSize = 4096
#IpcLinkSupervisionInterval = 1000
#IpcLinkProbeRetrials = 16		# def = 16. Antal obesvarade innan fel

#IpcDebugBufferSize = 3000
#IpcDebugLevel = 3
#IpcLostLinkDumpInfo=(0,0,0)
#IpcLostContactDumpInfo=(5,1,0)
#IpcIsolatedProcessorDumpInfo=(1,1)

#UdpAdaptionDrvPoolSize = 1000
#UdpAdaptionDrvBigPoolSize = 50

#Ddb_vitalTrace =  (237)		# Trace vid checkAllMdps
# Ddb_majorTrace =  (235)
#Ddb_vitalTrace =  (229)
#Ddb_detailTrace =  (229)
# Ddb_minorTrace = (44)

# DB table sizes
DdbRecordTabMasterSize = 1000000
DdbMdpTabSize = 1000
#DdbIndexSize = 100
#DdbInstanceTabSize = 100
DdbRecordTabLazySize = 100000   # old value was 100
#DdbOpenObjTabSize = 100
#DdbClassTabSize = 100

DdbBackupLoadmoduleSectionSize = 0x3D0900

# The `dumpd' tool should be used to retrieve dumps on a
# Unix host. Type `dumpd -h' to get help for `dumpd'.
# The dump files are ASCII-text (for now) and are stored in the
# directory where `dumpd' is started. The filenames are
#
#       DicosTextDump-n                 For Capsule dumps
#       DicosProcessorTextDump-n        For Processor dumps
#
# Where `n' is an index.
# The dump files are analyzed with the `epelfaddr_dmp' script.
 
# DUMP_MODE: bit 0 -    Console dump
#            bit 1 -    Remote Capsule Dump
#            bit 2 -    Remote Processor Dump
# '1' means "ON", to turn everything on set DUMP_MODE = 7
DUMP_MODE = 7
 
# DUMP_HOST_ID: The IP-address of the host where `dumpd' is running
DUMP_HOST_ID = (134,138,70,25)
 
# The UDP-port that `dumpd' listens on.
# The default port for `dumpd' is 5556.
DUMP_HOST_PORT = 5556
 
# DUMP_GATEWAY_1
# DUMP_GATEWAY_2 : IP-gateways to the `DUMP_HOST_ID'
# (these should be omitted if gateways are not needed)
#DUMP_GATEWAY_1 = (134,138,18,1)
#DUMP_GATEWAY_2 = (134,138,17,1)
 
# DUMP_DRIVER: The name of the driver for remote dumps,
# should always be "DumpDriverTftp" for now.
DUMP_DRIVER = "DumpDriverTftp"
#
# End of dump tool stuff
 

#NTP Time Service

NTP_POLL_INTERVAL = 64
# The IP and port of the NTP server (port = 123 is default)
#NTP_SERVER_IP = (134,138,128,17)
NTP_SERVER_PORT = 123

# TIME_TZ_OFFSET is the Local Time Zone offset in hours.
# Because only positive numbers can be given here the number is adjusted:
# intOffset = (TIME_TZ_OFFSET 12) ? TIME_TZ_OFFSET-24 : TIME_TZ_OFFSET;
TIME_TZ_OFFSET = 1

# Daylight Saving Time dates.
# This array consists of pairs: YYYYMMDDHH,offset
# The date is the non DST adjusted local (not UTC) time when the
# local time is altered. The offset is in hours. On the northen
# hemisphere you might set offset=1 in Mars and restore to
# offset=0 in October.
TIME_DST_DATES = ( 1999032802,1,  1999103102,0)

# Java Virtual Machine (JVM)
# To avoid lack of memory in the JVM, perform the following settings.
# The sizes are in Mega-byte. Default values are 4Mbyte for the JVM, and
# 8Mbyte for the entire JVM-Capsule.
# JAVA_HEAP - Is the size available for Java-code and Java-data.
#             The size must be big enough to hold all your (un-packed)
#             application classes, and all data (objects).
#             Maximum value seems to be 11Mbyte.
# JAVA_CAPSULE_HEAP - Is OPTIONAL. If not specified it is set to
#             JAVA_HEAP+4Mbyte. The size must be big enough to hold the
#             entire JAVA_HEAP, plus the JVM-code and internal data,
#             AND all JavaJar-LMs that you load initially.
#             Maximum value seems to be 15Mbyte.
# The JavaJar-LMs are temporary stored on the Capsule-heap until the JVM
# is completely started.
JAVA_HEAP = 24
JAVA_CAPSULE_HEAP = 31

# Knuerr HW alarm
# Instead of using an IP address of the Knuerr in this epct file, a
# name (RMS) is used. Remember to set the IP address when setting the
# DNS values after the system is loaded, i.e. connect the name RMS to
# a valid Knuerr IP address. / Michel 990902
RMS_IP_ADDRESS = "RMS"
RMS_NO_CABINET_B = 1
RMS_MAX_TEMP = 60
RMS_POLL_INTERVAL = 15000

ENDDATA

Note:
The following overload parameters for IPC are recommended in an e-mail (Re: Changed IPC parameters) from Stefan Näslund (000412):

# Level where messages to not connected ports do not get through
IpcOverloadRejectLevels = (1000, 2000, 100000)
# Level where overload warning is sent for connected ports
IpcOverloadWarningLevels = (1000, 2000, 100000)
# Level where messages are aborted for connected ports
IpcOverloadAbortLevels = (2000, 4000, 100000)

Explanations:
Explanations to some of the initial data variable names:

DdbLazyPurgeInterval       (How often lazy copies are removed, 60000=60 sec)
DdbRecordTabLazySize       (Size of table containing contemporary lazy copies)
DdbRecordTabMasterSize
DdbMdpTabSize

File processor.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

PROCESSOR Processor1 
        INITIAL
        TARGET i486 
        TYPE DcpsimEmMo 
        LOADER 
        ADDRESS "00:80:50:00:ce:e1 00:80:50:00:92:e0"
        IN DicosCommonPool,DicosPlgLoaderPool,DicosDbReplicaPool,DicosQnPool;

PROCESSOR Processor2 
        TARGET i486 
        TYPE DcpsimEmMo
        LOADER
        ADDRESS "00:80:50:00:88:f0 00:80:50:00:46:1f" 
        IN DicosCommonPool,DicosPlgLoaderPool,DicosDbReplicaPool,DicosQnPool;

PROCESSOR Processor3 
        TARGET i486 
        TYPE DcpsimEmMo 
        ADDRESS "00:80:50:00:8c:ae 00:80:50:00:46:2a" 
        IN DicosCommonPool;

PROCESSOR Processor4 
        TARGET i486 
        TYPE DcpsimEmMo 
        ADDRESS "00:80:50:00:88:d1 00:80:50:00:46:54" 
        IN DicosCommonPool;

PROCESSOR Processor5 
        TARGET i486 
        TYPE DcpsimEmMo 
        ADDRESS "00:80:50:00:8c:a5 00:80:50:00:46:26" 
        IN DicosCommonPool;

PROCESSOR Processor6 
        TARGET i486 
        TYPE DcpsimEmMo 
        ADDRESS "00:80:50:00:8c:6e 00:80:50:00:46:24" 
        IN DicosCommonPool;

PROCESSOR Processor7 
        TARGET i486 
        TYPE DcpsimEmMo 
        ADDRESS "00:80:50:00:8c:64 00:80:50:00:46:53" 
        IN DicosCommonPool;

File netred.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

SOFTWARE
	IDP/D2;		// NetRed_IDP, Optional

PROCESSOR Processor1 ALSO IN DicosNetRedPool,DicosNetRedConnectPool;
PROCESSOR Processor2 ALSO IN DicosNetRedPool,DicosNetRedConnectPool;
PROCESSOR Processor3 ALSO IN DicosNetRedPool;
PROCESSOR Processor4 ALSO IN DicosNetRedPool;
PROCESSOR Processor5 ALSO IN DicosNetRedPool;
PROCESSOR Processor6 ALSO IN DicosNetRedPool;
PROCESSOR Processor7 ALSO IN DicosNetRedPool;

File demo.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

SOFTWARE
	IDP/DEA9990;	// Demo_IDP, Optional

PROCESSOR Processor1 ALSO IN TrafficGeneratorPool;
PROCESSOR Processor2 ALSO IN TrafficGeneratorPool;
PROCESSOR Processor3 ALSO IN ApplicationPool;
PROCESSOR Processor4 ALSO IN ApplicationPool;
PROCESSOR Processor5 ALSO IN ApplicationPool;
PROCESSOR Processor6 ALSO IN ApplicationPool;
PROCESSOR Processor7 ALSO IN ApplicationPool;

File java.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

SOFTWARE
	IDP/D1;		// JavaDemo_IDP, Optional

PROCESSOR Processor1 ALSO IN JavaDemoAppPool;
PROCESSOR Processor2 ALSO IN JavaDemoAppPool;
PROCESSOR Processor3 ALSO IN JavaDemoTGPool;
PROCESSOR Processor4 ALSO IN JavaDemoTGPool;
PROCESSOR Processor5 ALSO IN JavaDemoAppPool;
PROCESSOR Processor6 ALSO IN JavaDemoAppPool;
PROCESSOR Processor7 ALSO IN JavaDemoAppPool;

File omed.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

SOFTWARE
	IDP/Omed;	// Omed_IDP, Optional

PROCESSOR Processor1 ALSO IN OmedWorkPool;
PROCESSOR Processor2 ALSO IN OmedWorkPool;
PROCESSOR Processor3 ALSO IN OmedWorkPool;
PROCESSOR Processor4 ALSO IN OmedWorkPool;
PROCESSOR Processor5 ALSO IN OmedWorkPool;
PROCESSOR Processor6 ALSO IN OmedGeneratorPool;
PROCESSOR Processor7 ALSO IN OmedGeneratorPool;

File axmp.epct, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

axmp.epct does not yet exist for to3, since it does not have any AXmp HW.

SOFTWARE
	IDP/D8;		// Axmp_IDP, Optional

ENVIRONMENT DATA

AXMP_POLL_INTERVAL = "20000"
AXMP_ADDRESSES = "to3s7c1:9977,to3s7c2:9977"
AXMP_HIGH_TEMP = "50"
AXMP_VOLTAGE_INTERVAL = "24-33"

ENDDATA

File servicePlatform.epct with the applications AC, HLR and SCP, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

// Software Definitions
SOFTWARE
       
        IDG/SERVICEPLATFORM,
        IDG/HLR,
        IDG/AC,
        IDG/SCP,
        IDP/POPULATOR;

//ALLOCATE DfsCosNamingResponder_DUT TO DbaPool;	
INITIAL DATA

# The following are our two SS7 Machines
The_IP_Address = "134.138.187.8"
The_IP_Address_Dual = "134.138.187.8"
Count_IP_Port	= 3
The_IP_Port = 8001		#Old HLR (SSN5), HLR protocol rev A
The_IP_Port2 = 8002		#New HLR (SSN6), HLR protocol rev B+
The_IP_Port3 = 8003		#AC (SSN10)
#The_IP_Port4 = 8004		#SCP (SSN55)

The_Second_IP_Address = "134.138.187.9"
The_Second_IP_Address_Dual = "134.138.187.9"
Count_Second_IP_Port = 3
The_Second_IP_Port = 8001	#Old HLR (SSN5), HLR protocol rev A
The_Second_IP_Port2 = 8002	#New HLR (SSN6), HLR protocol rev B+
The_Second_IP_Port3 = 8003	#AC (SSN10)
#The_Second_IP_Port4 = 8004	#SCP (SSN55)

Count_SS7_Activated = 2

MonitorTableSize = 16384
SignallerTableSize = 2048

MaxPortNamePublications = 4000

Ddb_majorTrace = (245)

ENDDATA

File pools.epct with the applications AC, HLR and SCP, located at e.g.
`/home/dicostest/tosFiles/to3/ad12/` Back to Contents

PROCESSOR Processor1 ALSO IN DbaPool,PopExePool;
PROCESSOR Processor2 ALSO IN DbaPool,PopExePool;
PROCESSOR Processor3 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor4 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor5 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor6 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;
PROCESSOR Processor7 ALSO IN DistributorPool,HlrPool,AcPool,ScpPool,PopPool;

File Jambala.epct Back to Contents

// Jambala.epct
// ------------

//  Revision History
//  ----------------
//  1999-09-30  lmcbetr		Rename from ServicePlatform.epct to Jambala.epct
//					Put all software in Jambala.epct and all INITIAL DATA in 
//					JambalaData.epct


////// Configuration Name
// build the name of the configuration using version of applications.
// use the name generated by the build process (see http://panam.lmc.ericsson.se/tcm_k/cgi/convention.txt)
// but replace '.' by '_'

NAME JAM_PL_1_1_12_SCP_2_0_5;

////// Zone
// For network redundancy to find out what network the system belongs to.
// ZONE 1 is default if not typed, the redundant network should be named
// ZONE 2.

ZONE 1;


////// Software 
// list all IDG, IDP or LM required for the configuration
// don't forget the semi-colon (;) at the end

SOFTWARE
   //TelOrb software
       IDP/MD14    // Dicos_IDP 
      ,IDP/MD16    // Ethernet Loading and Communication
      ,IDP/DUO2    // Net_IDP, to show load on processors 
//      ,IDP/D2      // NetRed_IDP, (optional)
//      ,IDP/D3      // Hardware Alarm collector (optional)
//      ,IDP/MD17    // LoadLinkUdpAdaptation_IDP (optional)
      ,IDP/MD18    // Java VM, (optional, required for the Scp)

  // Jambala Software
      ,IDG/SERVICEPLATFORM         // base for all applications
      ,IDG/HLR
      ,IDG/AC
      ,IDG/SCP
	;

File JambalaData.epct Back to Contents

// JambalaData.epct 
// ----------------
//  
//  Revision History
//  ----------------
//  1999-09-30  lmcbetr		Rename from TelOrb.epct to JambalaData.epct
//                            Add documentation on a few tags after uablrek comments
//					Increase SignallerTableSize to 3000
//					Increase TimeoutTableSize to 32767
//					Put all software in Jambala.epct and all INITIAL DATA in 
//					JambalaData.epct
//
//  1999-09-29  lmcbetr		Complete revision, merge of Ethernet.epct, Net.epct, Data.epct
//					TelOrb.epct, UdpLoading.epct, NTP.epct
//


INITIAL DATA
#### Comments in initial data section must start with '#'

### SHELL ports
# port address base for the telnet shell
# add the index of the processor you are trying to connect to
# e.g. 8014 for processor 5
ShellTelnetPortNoBase = 8010

# port address base for the http connection
# add the index of the processor you are trying to connect to
# e.g. 5614 for processor 5
ShellHttpPortNoBase = 5610

### Q-Util
# port address for the Q-Util shell
KernelUtilityDaemonPort = 42015   


### ORB
# Host address of IIOP gateway
# normally it is the names of the first two processors
DorbIIOPHostName = "TelorbProc1:TelorbProc2"
DorbIIOPPort = 56001

# When 1 telorb prints the IOR on the console
IOR_PRINT = 1

# tracing (0 = OFF, 1 = ON)
IIOP_GatewayVerbose = 0


### DBN record table size
# Max objects/processor including replication
# Example: 1000000 subscribers each consisting of 10 POT (objects) with 
# replicas and a margin for backup and reconfiguration.
# (1000000 * 10 * 2 * 2) / (28 - 1) rounded is 1500000 and then an 
# 10% margin extra gives 1650000
# Explanations
# (maximum number of subscribers when the system is fully configured for 
# this number of processors) * (POT (objects) per subscriber) * 
# (doubling for replicas) * (doubling for backup) / (number of processors) - 
# (compensate that one processor can be out of service, that gives the 
# margin for reconfiguration(if the loaders are not used for normal
# traffic they should be withdrawn as well)) 
# Check memory cost afterwards, it is 16B x DdbRecordTabMasterSize
# DB table sizes
### For Ac, we have only one POT (AuthData)
### For Hlr, we estimate to 7 (HlrSubscriber, StoredLocation + 5 services)
### for Platform, we have 3 POTs (Min, Dirnum, basicSubscriber) POTs per subscriber
### For Scp, we estimate to 7 POTS (ScpSubscriber (individual or group) + 6 POTs for services,
###         (some Scp services needs more than one pot )
### for Argentina, we supposed 200000 Scp subscribers, over 5 traffic processors
DdbRecordTabMasterSize = 2200000


### MDP
# How many Mdp objects (DU:s with POT:s) that can be in the table,
# rounded upwards
# ((HlrSubscriber+ScpSubscriber+ScpGroup+AcSubscriber+BasicSubscriber+Min+Dirnum+Esn) * 911) = 7300
#  + All other keyed POTs (1 DU per DUT)
# ?maybe 8000 is enough?
#  [is there any Mdp in Telorb that we have to count?]
DdbMdpTabSize = 10000


### Garbage Collecting for Lazy copy of data.
# This is the interval in which the DBMS lazy record table is
# iterated through  to remove copies from a processor.
# UAB Recommended value is 60 seconds.
DdbLazyPurgeInterval = 60000           

# Lazy copy table size (uab recommended value = 100000)
DdbRecordTabLazySize = 100000

### BACKUP
# uncompressed LM size for target systems 4MByte or 0x3D0900
# (size for Vega simulated systems 1MByte or 0xF4240)
DdbBackupLoadmoduleSectionSize = 0x3D0900 

#### dump tool configuration and usage
#
# The `dumpd' tool should be used to retrieve dumps on a
# Unix host. Type `dumpd -h' to get help for `dumpd'.
# The dump files are ASCII-text (for now) and are stored in the
# directory where `dumpd' is started. The filenames are
#
#       DicosTextDump-n                 For Capsule dumps
#       DicosProcessorTextDump-n        For Processor dumps
#
# Where `n' is an index.
# The dump files are analyzed with the `epelfaddr_dmp' script.
 
# DUMP_MODE: bit 0 -    Console dump
#            bit 1 -    Remote Capsule Dump
#            bit 2 -    Remote Processor Dump
# '1' means "ON", to turn everything on set DUMP_MODE = 7
DUMP_MODE = 7
 
# DUMP_HOST_ID: The IP-address of the host where `dumpd' is running
#DUMP_HOST_ID = (134,138,25,107) # this is used instead in the bootptab,T151 
 
# The UDP-port that `dumpd' listens on.
# The default port for `dumpd' is 5556.
DUMP_HOST_PORT = 5556
 
# DUMP_GATEWAY_1
# DUMP_GATEWAY_2 : IP-gateways to the `DUMP_HOST_ID'
# (these should be omitted if gateways are not needed)
#DUMP_GATEWAY_1 = (134,138,18,1)
#DUMP_GATEWAY_2 = (134,138,17,1)
 
# DUMP_DRIVER: The name of the driver for remote dumps,
# should always be "DumpDriverTftp" for now.
DUMP_DRIVER = "DumpDriverTftp"
#
# End of dump tool stuff


### Time service 
# The IP and port of the NTP server (port = 123 is default) 
# NTP_SERVER_IP = (134,138,25,107) # this is used instead in the bootptab 
NTP_SERVER_PORT = 5566

# TIME_TZ_OFFSET is the Local Time Zone offset in hours.
# Because only positive numbers can be given here the number is adjusted:
# intOffset = (TIME_TZ_OFFSET > 12) ? TIME_TZ_OFFSET-24 : TIME_TZ_OFFSET;
TIME_TZ_OFFSET = 19

### INITIAL DATA for the optional Java IDP, if used remove the comments
# Java Virtual Machine (JVM)
# To avoid lack of memory in the JVM, perform the following settings.
# The sizes are in Mega-byte. Default values are 4Mbyte for the JVM, and
# 8Mbyte for the entire JVM-Capsule.
# JAVA_HEAP - Is the size available for Java-code and Java-data.
#             The size must be big enough to hold all your (un-packed)
#             application classes, and all data (objects).
#             Maximum value seems to be 27Mbyte.
# JAVA_CAPSULE_HEAP - Is OPTIONAL. If not specified it is set to
#             JAVA_HEAP+4Mbyte. The size must be big enough to hold the
#             entire JAVA_HEAP, plus the JVM-code and internal data,
#             AND all JavaJar-LMs that you load initially.
#             Maximum value seems to be 31Mbyte.
# UAB Recommendation : always use the maximum values for the SCP
# The JavaJar-LMs are temporary stored on the Capsule-heap until the JVM
# is completely started.
#JAVA_HEAP = 4  # default value, see explanation above for your own value
JAVA_HEAP = 22
JAVA_CAPSULE_HEAP = 31


### INITIAL DATA for the optional Hardware Alarms Collector
# (KnuerrRms_IDP). If used remove the comments.
# Knuerr HW alarm
# The IP address for the Hardware Alarms Collector (Knuerr RMS)
# Replace this IP address with your local IP address
RMS_IP_ADDRESS = "134.138.187.101"

## RMS_NO_CABINET_B = 0, the system consist of two cabinets
## RMS_NO_CABINET_B = 1, the system consist of one cabinet
RMS_NO_CABINET_B = 1
## magic numbers...
RMS_MAX_TEMP = 60
RMS_POLL_INTERVAL = 15000


### IPC parameters
# Level where messages to not connected ports do not get through
IpcOverloadRejectLevels = (100, 200, 50000)
# Level where overload warning is sent for connected ports
IpcOverloadWarningLevels = (100, 200, 50000)
# Level where messages are aborted for connected ports
IpcOverloadAbortLevels = (400,800, 100000)


#### NETWORK REDUNDANCY
# These values are magic numbers provided by UAB to LMC
DdbExtSynchNoOfProcesses = 5
DdbnrProcBacklogBytes = 90000000
DdbnrNoOfPseudoParticipants = 30


### MonitorTableSize 
# Default = 2047 (way too low!!)
# The maximum number of simultaneous monitors on a processor.
# Monitors are mainly used by the JVM .
# UAB recommandation: 16384 seems reasonable, maybe a little low.
MonitorTableSize = 16384


### SignallerTableSize 
# Default = "NotificationTableSize" = 256 (way too low!!)
# The maximum number of simultaneous signallers on a processor.
# Signallers are used for entering a job in the job-queue to a thread.
# They are used to wake up the "Process Threads" in Java, and for resuming
# execution on a synchronous file-system access (among other things).
# You will need at least one per simultaneous Java process, and one per
# outstanding file-system operation.
# UAB recommandation: 2048 seems a little low.
SignallerTableSize = 3000


### MaxPortNamePublications 
# Default = 2000
# The maximum number of named ports in the system (not processor this time).
# Named ports are used for server processes. Each process type (not process
# instance) publishes a port per processor it is allocated to.
# UAB recommandation: 4000 seems Ok.
MaxPortNamePublications = 4000


### TimeoutTableSize 
# Default =  2047 (way too low!!)
# The maximum number of simultaneously running timers. This is
# impossible to estimate. Timers are used everywhere.
# I think the memory usage is only 1 pointer (4 byte) per entry in
# the table so I think you can increase the value without running out of
# memory.
# UAB recommandation: --- 16383 I would double it just to be sure :-)
TimeoutTableSize = 32767

### ScpProcess INITIAL DATA
# this identifies the ScpProcess process to be used by the distributor
# valid values are
# "ScpProcess" : (default) java process
# "ScpTrafficFramework" : C++ process
ScpFactory_processName = "ScpProcess"
        
#### Distributor INITIAL DATA
# Connection to the SS7 stacks and the wrapper
# Provide 2 ip addresses per stack
# and the ip port to connect to
# must match with the wrapper configuration
# There should be one port per SSN.

# number of stacks
Count_SS7_Activated = 2

# first stack
The_IP_Address = "172.16.1.151"
The_IP_Address_Dual = "172.17.1.151"
Count_IP_Port        = 6
The_IP_Port = 8001
The_IP_Port2 = 8002
The_IP_Port3 = 8003
The_IP_Port4 = 8004
The_IP_Port5 = 8005
The_IP_Port6 = 8006

# second stack
The_Second_IP_Address = "172.16.1.152"
The_Second_IP_Address_Dual = "172.17.1.152"
Count_Second_IP_Port = 6
The_Second_IP_Port = 8001
The_Second_IP_Port2 = 8002
The_Second_IP_Port3 = 8003
The_Second_IP_Port4 = 8004
The_Second_IP_Port5 = 8005
The_Second_IP_Port6 = 8006


###  OLD TAGS REMOVED  
#
# NTP_POLL_INTERVAL shall not be used anymore.
#
# The TIME_DST_DATES just specifies a default on initial start.
# The best on a real system is probably to omit this totally, and
# enter the DST-dates via the CORBA interface when the system is
# started, and then take a backup (the DSTs are stored in the database).
#
# IpcPortTableSize does not have to be specified, the default value 
# (32767) is ok.
# 
# Trace tags shall be removed.
# (DEBUG_MODE, DbdPOTLoadTrace, Ddb_majorTrace, HEAP_DEBUG, Ddb_vitalTrace, ...)
# 


ENDDATA

File Processor.epct Back to Contents

// Processor.epct
// --------------
//
//	Revision History
//	----------------
//
//    1999-09-30  lmcbetr       Cleanup, add redundancy pools.


/// Set ethernet address according to the hardware configuration of the system.
/// And create enough processor for the actual system
PROCESSOR Processor1
     INITIAL
     TARGET i486 
     TYPE DcpsimEmMo
     LOADER
     ADDRESS "00:80:50:00:cb:0b 00:80:50:00:8f:f9"
     IN DicosCommonPool, DicosPlgLoaderPool, DicosDbReplicaPool, DicosQnPool;
PROCESSOR Processor2
     TARGET i486 
     TYPE DcpsimEmMo
     LOADER
     ADDRESS "00:80:50:00:cb:00 00:80:50:00:8f:de"
     IN DicosCommonPool, DicosPlgLoaderPool, DicosDbReplicaPool, DicosQnPool;
PROCESSOR Processor3
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:cb:21 00:80:50:00:8e:f5" 
     IN DicosCommonPool;
PROCESSOR Processor4
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:ca:ff 00:80:50:00:8e:e1" 
     IN DicosCommonPool;
PROCESSOR Processor5
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:c9:82 00:80:50:00:8a:55"
     IN DicosCommonPool;
PROCESSOR Processor6
     TARGET i486 
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:cb:03 00:80:50:00:8e:c5" 
     IN DicosCommonPool;
PROCESSOR Processor7
     TARGET i486
     TYPE DcpsimEmMo
     ADDRESS "00:80:50:00:ca:f9 00:80:50:00:8e:d9"
     IN DicosCommonPool;



/// Other TelOrb Pools
/// If an application or function is not installed,
/// just comment out the corresponding pool.
///
/// NetworkRedundancy  (IDP/D2)
/// -----------------

PROCESSOR Processor1 ALSO IN DicosNetRedPool, DicosNetRedConnectPool;
PROCESSOR Processor2 ALSO IN DicosNetRedPool, DicosNetRedConnectPool;
PROCESSOR Processor3 ALSO IN DicosNetRedPool;
PROCESSOR Processor4 ALSO IN DicosNetRedPool;
PROCESSOR Processor5 ALSO IN DicosNetRedPool;
PROCESSOR Processor6 ALSO IN DicosNetRedPool;
PROCESSOR Processor7 ALSO IN DicosNetRedPool;


/// Jambala pools
///
/// DbaPool  (IDG/SERVICEPLATFORM)
/// -------

PROCESSOR Processor1 ALSO IN DbaPool;
PROCESSOR Processor2 ALSO IN DbaPool;

/// DistributorPool (IDG/SERVICEPLATFORM)
/// ---------------

PROCESSOR Processor3 ALSO IN DistributorPool;
PROCESSOR Processor4 ALSO IN DistributorPool;
PROCESSOR Processor5 ALSO IN DistributorPool;
PROCESSOR Processor6 ALSO IN DistributorPool;
PROCESSOR Processor7 ALSO IN DistributorPool;


/// AcPool (IDG/AC)
/// ------

PROCESSOR Processor3 ALSO IN AcPool;
PROCESSOR Processor4 ALSO IN AcPool;
PROCESSOR Processor5 ALSO IN AcPool;
PROCESSOR Processor6 ALSO IN AcPool;
PROCESSOR Processor7 ALSO IN AcPool;

/// HlrPool (IDG/HLR)
/// -------

PROCESSOR Processor3 ALSO IN HlrPool;
PROCESSOR Processor4 ALSO IN HlrPool;
PROCESSOR Processor5 ALSO IN HlrPool;
PROCESSOR Processor6 ALSO IN HlrPool;
PROCESSOR Processor7 ALSO IN HlrPool;


/// ScpPool (IDG/SCP)
/// -------

PROCESSOR Processor3 ALSO IN ScpPool;
PROCESSOR Processor4 ALSO IN ScpPool;
PROCESSOR Processor5 ALSO IN ScpPool;
PROCESSOR Processor6 ALSO IN ScpPool;
PROCESSOR Processor7 ALSO IN ScpPool;

File dhcpd.pxe.conf on IO processor 1 without terminal server, located at `/etc/` Back to Contents

# This is a template dhcpd configuration file for use by
# the ISC version 3 dhcpd.

# Replace all the words written in CAPITALS with appropriate values.
# Ip addresses can be written with 'dot notation' or symbolic name.
# Ethernet addresses are written as b5:b4:b3:b2:b1:b0.


option time-offset 3600;

# Ip address of timeservers 
option time-servers 134.138.59.25, 134.138.60.26;

# define site specific options
option epTftpdServerAddress    code 152 = ip-address;
option dumpServerAddress       code 153 = array of ip-address;
option consoleServerAddress    code 154 = array of ip-address;
option consoleServerPort       code 155 = unsigned integer 16;


# define the dicos processors

# wrap all the dicos processors into one shared network inorder to
# get dhcpd to answer bootp requests regarding interfaces on other
# networks.
shared-network dicosProcessor {

   subnet 134.138.59.0 netmask 255.255.255.0 {
      option routers 134.138.59.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.59.255;
      next-server 134.138.59.25;
   }

   subnet 134.138.60.0 netmask 255.255.255.0 {
      option routers 134.138.60.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.60.255;
      next-server 134.138.60.25; 
   }

   option dumpServerAddress    134.138.59.25, 134.138.60.26; 
   option consoleServerAddress 134.138.59.25;
   option consoleServerPort    7000;

# Uncomment one of the following lines if the dicosProcessors are going to be
# booted by the smallProm or bootp netboot.
# For PXE the 'filename' must NOT be used.

# on solaris use next line
  filename "telorb/ppro/pl";

# on linux use next line
# filename "/tftpboot/telorb/ppro/pl";

#   if doing PXE boot uncomment next lines
#    class "pxeclient" {
#        match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
#       option vendor-class-identifier "PXEClient";
#   }
}

# define the external network aswell, note it is outside the
# scope of the shared network dicosProcessors.

subnet 134.138.184.0 netmask 255.255.248.0 {
   option routers 134.138.184.1;
   option subnet-mask 255.255.248.0;
   option broadcast-address 134.138.191.255;
}

# define the processors

host p1_0 {
   hardware ethernet 00:30:f7:00:c7:b9;
   fixed-address     134.138.59.101;
# Processor 1 is usually a loader
   option epTftpdServerAddress 134.138.59.25;
}

host p1_1 {
   hardware ethernet 00:a0:a5:12:18:38;
   fixed-address     134.138.60.101;
# Processor 1 is usually a loader
   option epTftpdServerAddress 134.138.60.25;
}


host p2_0 {
   hardware ethernet 00:30:f7:00:c7:e9;
   fixed-address     134.138.59.102;
# Processor 2 is usually a loader
   option epTftpdServerAddress 134.138.59.25;
}

host p2_1 {
   hardware ethernet 00:a0:a5:12:18:27;
   fixed-address     134.138.60.102;
# Processor 2 is usually a loader
   option epTftpdServerAddress 134.138.60.25;
}


host p3_0 {
   hardware ethernet 00:30:f7:00:c7:82;
   fixed-address     134.138.59.103;
}

host p3_1 {
   hardware ethernet 00:a0:a5:12:18:26;
   fixed-address     134.138.60.103;
}


host p4_0 {
   hardware ethernet 00:30:f7:00:c7:bf;
   fixed-address     134.138.59.104;
}

host p4_1 {
   hardware ethernet 00:a0:a5:12:18:37;
   fixed-address     134.138.60.104;
}


host p5_0 {
   hardware ethernet 00:30:f7:00:c8:2f;
   fixed-address     134.138.59.105;
}

host p5_1 {
   hardware ethernet 00:a0:a5:12:18:3b;
   fixed-address     134.138.60.105;
}


host p6_0 {
   hardware ethernet 00:30:f7:00:c7:c1;
   fixed-address     134.138.59.106;
}

host p6_1 {
   hardware ethernet 00:a0:a5:12:18:33;
   fixed-address     134.138.60.106;
}


host p7_0 {
   hardware ethernet 00:30:f7:00:c7:58;
   fixed-address     134.138.59.107;
}

host p7_1 {
   hardware ethernet 00:a0:a5:12:18:1c;
   fixed-address     134.138.60.107;
}


host p8_0 {
   hardware ethernet 00:30:f7:00:c7:5c;
   fixed-address     134.138.59.108;
}

host p8_1 {
   hardware ethernet 00:a0:a5:12:18:1a;
   fixed-address     134.138.60.108;
}


host p9_0 {
   hardware ethernet 00:30:f7:00:c8:02;
   fixed-address     134.138.59.109;
}

host p9_1 {
   hardware ethernet 00:a0:a5:12:18:1b;
   fixed-address     134.138.60.109;
}


host p10_0 {
   hardware ethernet 00:30:f7:00:c1:e0;
   fixed-address     134.138.59.110;
}

host p10_1 {
   hardware ethernet 00:a0:a5:12:17:b6;
   fixed-address     134.138.60.110;
}


# define an entry for the xyplex

#host xyplex {
#   hardware ethernet ETH_ADDR_FOR_XYPLEX;
#   fixed-addr        IP_ADDR_FOR_XYPLEX;
#
##   for sparc
#   filename "telorb/xyplex/xpcsrv20.sys"
##   for linux
##   filename "/tftpboot/xyplex/xpcsrv20.sys"
#}

Note:

- The last lines (after and including the line "# define an entry for the xyplex") can be removed if a terminal server is not being used.

- You have to have super user privileges to be able to modify the file.

- The only differences between the dhcpd.pxe.conf files on IO1 and IO2 are the lines:

  next-server 134.138.59.25;                          (25 for IO1, and 26 for IO2)
  next-server 134.138.60.25;                          (25 for IO1, and 26 for IO2)

  option epTftpdServerAddress 134.138.59.25; (for P1) (25 for IO1, and 26 for IO2)
  option epTftpdServerAddress 134.138.60.25; (for P1) (25 for IO1, and 26 for IO2)
  option epTftpdServerAddress 134.138.59.25; (for P2) (25 for IO1, and 26 for IO2)
  option epTftpdServerAddress 134.138.60.25; (for P2) (25 for IO1, and 26 for IO2)

It is important that the IP address value for consoleServerAddress is the same in both IO processors, since it points to the IO processor where the STSSw is executing.

File dhcpd.pxe.conf on IO processor 2 without terminal server, located at `/etc/` Back to Contents

# This is a template dhcpd configuration file for use by
# the ISC version 3 dhcpd.

# Replace all the words written in CAPITALS with appropriate values.
# Ip addresses can be written with 'dot notation' or symbolic name.
# Ethernet addresses are written as b5:b4:b3:b2:b1:b0.


option time-offset 3600;

# Ip address of timeservers 
option time-servers 134.138.59.25, 134.138.60.26;

# define site specific options
option epTftpdServerAddress    code 152 = ip-address;
option dumpServerAddress       code 153 = array of ip-address;
option consoleServerAddress    code 154 = array of ip-address;
option consoleServerPort       code 155 = unsigned integer 16;


# define the dicos processors

# wrap all the dicos processors into one shared network inorder to
# get dhcpd to answer bootp requests regarding interfaces on other
# networks.
shared-network dicosProcessor {

   subnet 134.138.59.0 netmask 255.255.255.0 {
      option routers 134.138.59.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.59.255;
      next-server 134.138.59.26;
   }

   subnet 134.138.60.0 netmask 255.255.255.0 {
      option routers 134.138.60.1;
      option subnet-mask 255.255.255.0;
      option broadcast-address 134.138.60.255;
      next-server 134.138.60.26; 
   }

   option dumpServerAddress    134.138.59.25, 134.138.60.26; 
   option consoleServerAddress 134.138.59.25;
   option consoleServerPort    7000;

# Uncomment one of the following lines if the dicosProcessors are going to be
# booted by the smallProm or bootp netboot.
# For PXE the 'filename' must NOT be used.

# on solaris use next line
  filename "telorb/ppro/pl";

# on linux use next line
# filename "/tftpboot/telorb/ppro/pl";

#   if doing PXE boot uncomment next lines
#    class "pxeclient" {
#        match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
#       option vendor-class-identifier "PXEClient";
#   }
}

# define the external network aswell, note it is outside the
# scope of the shared network dicosProcessors.

subnet 134.138.184.0 netmask 255.255.248.0 {
   option routers 134.138.184.1;
   option subnet-mask 255.255.248.0;
   option broadcast-address 134.138.191.255;
}

# define the processors

host p1_0 {
   hardware ethernet 00:30:f7:00:c7:b9;
   fixed-address     134.138.59.101;
# Processor 1 is usually a loader
   option epTftpdServerAddress 134.138.59.26;
}

host p1_1 {
   hardware ethernet 00:a0:a5:12:18:38;
   fixed-address     134.138.60.101;
# Processor 1 is usually a loader
   option epTftpdServerAddress 134.138.60.26;
}


host p2_0 {
   hardware ethernet 00:30:f7:00:c7:e9;
   fixed-address     134.138.59.102;
# Processor 2 is usually a loader
   option epTftpdServerAddress 134.138.59.26;
}

host p2_1 {
   hardware ethernet 00:a0:a5:12:18:27;
   fixed-address     134.138.60.102;
# Processor 2 is usually a loader
   option epTftpdServerAddress 134.138.60.26;
}


host p3_0 {
   hardware ethernet 00:30:f7:00:c7:82;
   fixed-address     134.138.59.103;
}

host p3_1 {
   hardware ethernet 00:a0:a5:12:18:26;
   fixed-address     134.138.60.103;
}


host p4_0 {
   hardware ethernet 00:30:f7:00:c7:bf;
   fixed-address     134.138.59.104;
}

host p4_1 {
   hardware ethernet 00:a0:a5:12:18:37;
   fixed-address     134.138.60.104;
}


host p5_0 {
   hardware ethernet 00:30:f7:00:c8:2f;
   fixed-address     134.138.59.105;
}

host p5_1 {
   hardware ethernet 00:a0:a5:12:18:3b;
   fixed-address     134.138.60.105;
}


host p6_0 {
   hardware ethernet 00:30:f7:00:c7:c1;
   fixed-address     134.138.59.106;
}

host p6_1 {
   hardware ethernet 00:a0:a5:12:18:33;
   fixed-address     134.138.60.106;
}


host p7_0 {
   hardware ethernet 00:30:f7:00:c7:58;
   fixed-address     134.138.59.107;
}

host p7_1 {
   hardware ethernet 00:a0:a5:12:18:1c;
   fixed-address     134.138.60.107;
}


host p8_0 {
   hardware ethernet 00:30:f7:00:c7:5c;
   fixed-address     134.138.59.108;
}

host p8_1 {
   hardware ethernet 00:a0:a5:12:18:1a;
   fixed-address     134.138.60.108;
}


host p9_0 {
   hardware ethernet 00:30:f7:00:c8:02;
   fixed-address     134.138.59.109;
}

host p9_1 {
   hardware ethernet 00:a0:a5:12:18:1b;
   fixed-address     134.138.60.109;
}


host p10_0 {
   hardware ethernet 00:30:f7:00:c1:e0;
   fixed-address     134.138.59.110;
}

host p10_1 {
   hardware ethernet 00:a0:a5:12:17:b6;
   fixed-address     134.138.60.110;
}


# define an entry for the xyplex

#host xyplex {
#   hardware ethernet ETH_ADDR_FOR_XYPLEX;
#   fixed-addr        IP_ADDR_FOR_XYPLEX;
#
##   for sparc
#   filename "telorb/xyplex/xpcsrv20.sys"
##   for linux
##   filename "/tftpboot/xyplex/xpcsrv20.sys"
#}

Note:
The last lines (after and including the line "# define an entry for the xyplex") can be removed if a terminal server is not being used.

The only differences between the dhcpd.pxe.conf files on IO1 and IO2 are the lines:

next-server 134.138.59.26;                          (26 for IO2, and 25 for IO1)
next-server 134.138.60.26;                          (26 for IO2, and 25 for IO1)

option epTftpdServerAddress 134.138.59.26; (for P1) (26 for IO2, and 25 for IO1)
option epTftpdServerAddress 134.138.60.26; (for P1) (26 for IO2, and 25 for IO1)
option epTftpdServerAddress 134.138.59.26; (for P2) (26 for IO2, and 25 for IO1)
option epTftpdServerAddress 134.138.60.26; (for P2) (26 for IO2, and 25 for IO1)

It is important that the IP address value for consoleServerAddress is the same in both IO processors, since it points to the IO processor where the STSSw is executing.

File dhcptab on IO processor 1 without terminal server, located at `/var/dhcp/` Back to Contents

Locale	m	:UTCoffst=3600:
to3io1	m	:Include=Locale:Timeserv=134.138.70.25 134.138.74.26:LeaseTim=259200:LeaseNeg:DNSdmain=uab.ericsson.se:DNSserv=134.138.201.17 134.138.226.13:
ToEtftpS	s	Site,152,IP,1,1
ToDumpS	s	Site,153,IP,1,0
ToConS	s	Site,154,IP,1,2
ToConP	s	Site,155,NUMBER,2,1
telorbDumpS	m	:ToDumpS=134.138.70.25 134.138.74.26:
telorbConsoleS  m	:ToConS=134.138.70.25:ToConP=7000:
telorbDefaults  m       :Include=telorbDumpS:Include=telorbConsoleS:
default	m	:Include=Locale:Timeserv=134.138.70.25 134.138.74.26:
net184common	m	:Include=default:Subnet=255.255.248.0:Router=134.138.184.1:Broadcst=134.138.191.255:
net70common	m	:Include=default:Subnet=255.255.255.0:Router=134.138.70.1:Broadcst=134.138.70.255:
net74common	m	:Include=default:Subnet=255.255.255.0:Router=134.138.74.1:Broadcst=134.138.74.255:
net70telorb	m	:Include=net70common:Include=telorbDefaults:BootFile=telorb/ppro/pl:BootSrvA=134.138.70.25:
net74telorb	m	:Include=net74common:Include=telorbDefaults:BootFile=telorb/ppro/pl:BootSrvA=134.138.74.25:
net70telorbLoader	m	:Include=net70telorb:ToEtftpS=134.138.70.25:
net74telorbLoader	m	:Include=net74telorb:ToEtftpS=134.138.74.25:
#net184xyplex	m	:Include=net184common:BootFile=telorb/xyplex/xpcsrv20.sys:BootSrvA=134.138.187.20:

Note:
The last line can be removed if a terminal server is not being used. However, if a terminal server exists in the TelORB system (but is not being used), it is good to include the line, e.g. if another TelORB system wants to use the terminal server. In this case, it is not necessary to have this line included in the TelORB system that wants to use the terminal server.

When both IO processors are up and running, it is important that ToConS has the same value on both IO processors. For TelORB system to3, any combination of 70, 74, 25 and 26 is allowed, e.g. ToConS=134.138.70.25 or ToConS=134.138.74.26 or another combination. Be sure that the IO processor setting (e.g. to3io1) in file start_services corresponds to the ToConS setting.